home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000064_news@newsmaster….columbia.edu _Wed Jan 7 13:45:04 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA11297
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 7 Jan 1998 13:45:03 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA11981
for kermit.misc@watsun; Wed, 7 Jan 1998 13:45:02 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: K/2 gotchas
Date: 7 Jan 1998 18:44:58 GMT
Organization: Columbia University
Lines: 30
Message-ID: <690ifa$qik$1@apakabar.cc.columbia.edu>
References: <TCPSMTP.18.1.4.-14.19.44.2375661496.4900277@kincyb.com> <68qros$3ht$1@apakabar.cc.columbia.edu> <68r298$6ug$1@apakabar.cc.columbia.edu> <690ahp$q3b$1@samba.rahul.net>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:8234
In article <690ahp$q3b$1@samba.rahul.net>, <dold@network.rahul.net> wrote:
: Jeffrey Altman (jaltman@watsun.cc.columbia.edu) wrote:
: : My guess is that the ready for download or *** are either in a special
: : color, is bold faced, or is blinking. Which means that the real string
: : you are looking for contains ESC sequences. Therefore "ready for
: : download ***" is never actually seen.
:
: Log Session could be used to verify this.
:
Right. Another little-known but very handy feature of Kermit 95 is the
terminal-screen debugger. Just type Alt-d to toggle it on and off. When
on, the word DEBUG appears in the status line and all control characters and
escape sequences (and Telnet negotiations, etc) are shown graphically, in a
distinct color.
: I always Log Session before starting script design, to make sure that I
: don't make speeling mistakes or have cApitalization troubles, by
: editting the recorded file into a script, rather than entering from
: scratch.
:
And by the way, you can control whether INPUT commands care about
capitalization by using the command:
SET INPUT CASE { IGNORE, OBSERVE }
or, equivalently (and more simply):
SET CASE { ON, OFF }
- Frank